Skip to content

Conversation

sbahling
Copy link

Add awaited send_message functions for curio and trio implementations

In order to send a message over an awaited server socket (i.e. when you need external servers to reply to your listening server socket) the sock.sendto call needs to be awaited as well.

This commit adds async/await versions of the send_message and send_bundle functions that are called by the OSCCurioServer and OSCTrioServer send_message and send_bundle methods.

Strictly speaking, the async/await functions would probably not be used directly from the client module, so maybe there is a better place to put them. I tried to find ways to reduce code duplication as much as possible.

In order to send a message over an awaited server socket (i.e. when you
need external servers to reply to your listening server socket) the
sock.sendto call needs to also be awaited.

This commit adds async/await versions of the send_message and
send_bundle functions that are called by the OSCCurioServer and
OSCTrioServer send_message methods.
In order to send a message over an awaited server socket (i.e. when you
need external servers to reply to your listening server socket) the
sock.sendto call needs to also be awaited.

This commit adds async/await versions of the send_message and
send_bundle functions that are called by the OSCCurioServer and
OSCTrioServer send_message and send_bundle methods.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant